Ask users for Name
WCAG 2.2
New WCAG 2.2 criteria affects this pattern
To ask users for ‘Names’ and meet the new Web Content Accessibility Guidelines (WCAG) 2.2 criteria, make sure that users can successfully:
When to use this pattern
You should follow this pattern whenever you need to ask for a user’s name as part of your service. Only ask for people’s names if you need that information to deliver a service.
How it works
Make it as easy as possible for a user to enter their name. Always use two distinct fields for name input: one for the user's first name and one for their surname.
Example:
The only exception to the aforementioned two-field rule arises when requesting the names of the father and mother. In such instances, a single field for the full name may be used.
Example:
Make sure the fields work for most of your users
Fields must be long enough to accommodate the names of your users. You should use population data or data about your existing users to do this.
Support all the characters users may need to enter, including numbers and symbols.
Labelling name fields
Use:
- ‘Όνομα’
- ‘Επώνυμο
Reusing entered names
WCAG 2.2
Make sure users can easily reuse a previously entered name within a single journey, unless doing so would be a major safety or security concern. This is to comply with WCAG 2.2 success criterion 3.3.7 Redundant Entry.
You can make it easier to reuse names through one of these methods:
- pre-populate name fields with the previously entered name
- show any previously entered names as an option for the user to select
Avoid asking for a person’s title
Avoid asking users for their title.
It’s extra work for them and you’re asking them to potentially reveal their gender and marital status, which they may not want to do.
It’s also hard to predict the range of titles your users will have. If you have to ask for someone’s title, use an optional text input not a select.
Remember to correctly use people’s names in any resulting correspondence.